Clicking on a broken link is a pain, but a witty and well-designed error page at least sweetens the pill.
As an innovative, diverse and rapidly growing company Pointwest is currently developing an efficient electronic performance system. This application is created to ease the burden of assessing the capabilities and growth of an employee during his/her stay in the company.
Apparently, the team who handles the development of this application requested for designs of their error pages. Gathering some inputs from them and their perspective users, I have came up with some iniitial designs.
Not to undermine the importance of functionality, usability, and the service provided, but the emotional connection a user feels to the site will most often dominate their overall opinion about it. Below are my proposed designs:
The 404 page is a standard response code in HTTP telling the user, in effect, that they've clicked on a broken link.
The 404 page is a standard response code in HTTP telling the user, in effect, that they've clicked on a broken link.
This error can only be resolved by fixes to the Web server software. It is not a client-side problem. It is up to the operators of the Web server site to locate and analyze the logs which should give further information about the error.
The 401 Unauthorized error means the page you were trying to access needs valid user ID and password before you can view it.
The 403 Forbidden error is an HTTP status code which means that accessing the page or resource you were trying to reach is absolutely forbidden for some reason.
As software engineers and designers, there is little we can do about the unexpected. No matter how hard we try, some users will run into a dead end at some point. It might or not be our fault, but we should be prepared for when it happens.
Thanks!
